feat(service): LoadBalancer Service with DNS annotation#1426
Merged
Conversation
4764fcf to
b3bbbe8
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1426 +/- ##
==========================================
+ Coverage 77.96% 78.07% +0.10%
==========================================
Files 184 186 +2
Lines 24907 25129 +222
==========================================
+ Hits 19419 19619 +200
- Misses 4179 4194 +15
- Partials 1309 1316 +7
🚀 New features to boost your workflow:
|
4fcb4bf to
4cfcb3a
Compare
ec1e2bc to
d654146
Compare
28ccbf7 to
988758e
Compare
01e466f to
9406e73
Compare
TaoZou1
reviewed
Jun 9, 2026
Contributor
|
Could you also add the case if the nsx.vmware.com/hostname: has invalid input? |
9406e73 to
1c640e4
Compare
ggverma
reviewed
Jun 10, 2026
1c640e4 to
e1dc0cb
Compare
ggverma
approved these changes
Jun 11, 2026
6bb5887 to
6524644
Compare
yanjunz97
reviewed
Jun 12, 2026
534fc4d to
95a5b2a
Compare
wenyingd
commented
Jun 12, 2026
b6085d9 to
c2e7db5
Compare
yanjunz97
reviewed
Jun 16, 2026
yanjunz97
left a comment
Contributor
There was a problem hiding this comment.
Overall LGTM, just 2 nits
- Reconcile DNS records based on the `nsx.vmware.com/hostname` annotation on LoadBalancer Services using VPCNetworkConfiguration allowed DNS zones. - Support multiple comma-separated FQDNs in the annotation. - Report DNSRecordReady condition for DNS zone validation errors and generic DNS build errors.
c2e7db5 to
bb14d79
Compare
yanjunz97
approved these changes
Jun 17, 2026
Contributor
Author
|
/e2e |
TaoZou1
approved these changes
Jun 23, 2026
Contributor
Author
|
/e2e |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces the core capability to automatically manage DNS records for Kubernetes LoadBalancer Services. By annotating a Service with desired hostnames, the NSX operator will automatically provision and lifecycle the corresponding DNS records in NSX using the allocated External IPs, while strictly enforcing VPC-level DNS zone policies.
The following functions are delivered,
AI-Tool-Used: Cursor
AI-Tool-Use-Level: Category 2 (Medium)
AI-Code-Category: Category 1 (Production)
Test Done: